Requirements Engineering Process Research Articles

Toward a Holistic Privacy Requirements Engineering Process: Insights From a Systematic Literature Review

Toward a Holistic Privacy Requirements Engineering Process: Insights From a Systematic Literature Review

Challenges in Early Verification and Validation of System Requirements

ABSTRACTToday, requirements engineering (RE) is a key process in the development of complex systems‐(ISO/IEC/IEEE 2015). Requirements containing quality issues such as ambiguity or inconsistency can lead to late error detection in systems design, resulting in high project cost overruns. This paper presents challenges for early system requirements verification and validation associated to an executable model‐based requirements engineering (eMBRE) process proposal.

An AHP-Based Framework for Effective Requirement Management in Agile Software Development (ASD)

In Agile changes may be made at any time throughout the project lifetime in agile projects. These changes, however, often lead to longer turnaround times and higher costs while having a substantial influence on the activities and quality of project management. The suggested framework's main goal is to increase the effectiveness and flexibility of the requirement engineering process by successfully managing requirements changes, particularly in contexts where Agile Software Development (ASD) is practiced. The Agile methodology has gained popularity as a strategy for developing software because it can adjust to changing requirements and deliver software gradually. To make sure that the software being produced satisfies stakeholder expectations and adds value to the firm, good requirement management is essential. Using the Analytic Hierarchy Process (AHP) to prioritize requirements based on their relative relevance and urgency, this article introduces a framework for requirement management in Agile Projects. The most important requirements are taken care of first thanks to this strategy, which enables a more organized and informed decision-making process. We demonstrate the actual use of our framework in real-world contexts and highlight its efficacy in solving the issues faced by Agile projects by including a case study and an accompanying table. The suggested framework also supports the three core tenets of the Agile approach—transparency, cooperation, and continuous improvement—to foster an environment of excellence and ongoing learning within the Agile team. By developing these fundamental ideas, our framework not only supports Agile teams' continual growth and development but also helps them manage and prioritize requirements more efficiently, which ultimately improves project results and increases organizational value.

Joint Impact of Agents and Services in Enhancing Software Requirements Engineering

Requirements engineering (RE) is a significant aspect of system development stages in generating reliable software (SW). Despite RE’s decisive impact on project success, SW systems still fail since there is a perplexity in sorting out requirements correctly. Researchers have tried several paradigms to deal with the specified challenges, such as agent-oriented RE (AORE), model-based RE, and service-oriented RE (SORE). By investigating the limitations of the independent use of these paradigms, this research sets an objective that proposes a framework which integrates the two paradigms (agent and service) on top of social media to enhance the SW RE processes. Thus, the research addresses challenges in gathering adequate requirements, detecting alignment between business requirements and SW products, prioritizing requirements, and recommending innovative ideas. The research has mainly adopted an empirical research methodology for SW engineering. Accordingly, two distinct expert groups have been formed based on their previous experience in AORE and SORE, respectively. The experts have been selected from enterprises and academic institutions, and they participated in our case study. After performing the necessary assessment based on specified criteria, those experts in the first group have reported that CASCRE (Collaboration of Agents and Services for Crowd-based Requirements Engineering) with a score of 93.7% is found to be better than that of AORE with a score of 88.7%. Moreover, experts in the second group have declared that CASCRE, with a score of 92.3%, is better than SORE, with a score of 83.7%. In both cases, improvements have been observed, which reveals that the synergy of the CASCRE features has a better impact on the RE process than utilizing individual approaches. Moreover, in order to demonstrate the applicability of CASCRE, feedback has been gathered from a focused crowd of local pharmaceuticals using a mini-prototype. Accordingly, 250 requirements related comments have been gathered from the discussion forum, and 1400 keywords were generated. Then, after performing a sentiment analysis using NLP algorithms, the result was demonstrated to experts. Therefore, 93% of gurus strongly agreed on the applicability of CASCRE in real projects.

Sustaining human health: A requirements engineering perspective

In our current day and age, Earth suffers under the human ecological footprint, which influences our health and well-being. Technological solutions, including software-related ones, may help tackle these concerns for humanity. However, the development of such solutions requires special attention and effort to overcome human, public, and social barriers that might prevent them from being effective. The Requirements Engineering for Well-Being, Aging, and Health (REWBAH) workshop gathering in 2021 focused on addressing the challenge of how Requirements Engineering (RE) knowledge and practices can be applied to the development of information systems that support and promote long-lasting, sustained, and healthier behavior and choices by individuals. An interactive discussion among subject matter experts and practitioners participating in the REWBAH’21 revolved around several questions. In a subsequent qualitative analysis, the emerging themes were arranged in the sustainable-health RE (SusHeRE) framework to describe RE processes that address both sustainability and health goals. In this vision paper, we present our framework, which includes four main SusHeRE goals defined according to the changes in RE that we deem necessary for achieving a positive contribution of RE on sustainability and health. These goals involve improved RE Techniques, Multidisciplinary Expertise, Education Agenda, and Public and Social Ecology.

Towards understanding the influence of personality and team behaviors on requirements engineering activities

<span lang="EN-US">Requirements engineers play an important role in the development of software products and services. The nature of requirements engineering (RE) is multifaceted and influences the quality, success, or failure of software products. In gathering software requirements, engineers commonly work in a team, particularly when dealing with the customers or modeling the requirements, hence the team behavior may influence the RE activities. The investigation of requirements engineers’ personality and their team behavior associated with RE activities is still an open area in which research is still developing. This study aims to investigate the personality and team behavior of requirements engineers involved in RE activities using a systematic literature review approach. We included 64 primary studies that addressed the association between personality and team behavior of requirements engineers on the effectiveness of RE activities. The result shows that among personality dimensions, extraversion and conscientiousness were found to be the predominant personality traits that positively affect RE activities. Furthermore, team behavior of requirements engineers such as flexibility, collaboration, creativity, innovation, and norms were discovered as factors that influence the RE process, performance, and success. The findings of this study contribute to the body of knowledge and practice of RE by providing empirical evidence on the influence of requirements engineers’ personality and team behavior on the effectiveness of RE activities.</span>

Automatic Requirements Engineering: Activities, Methods, Tools, and Domains – A Systematic Literature Review

Requirements engineering (RE) is an initial activity in the software engineering process that involves many users. The involvement of various users in the RE process raises ambiguity and vagueness in requirements modeling. In addition, traditional RE is a time-consuming activity. Therefore various studies have been conducted to support process automation on RE. This paper conducts a systematic literature review (SLR) to obtain information about RE automation related to RE activities, methods/models, tools, and domains. SLR is done through 5 main stages: definition of research questions, conducting the search, screening for relevant papers, data extraction, mapping, and analysis. The data extraction and mapping are carried out on 155 relevant publications from 2016 to 2022. Based on the results from SLR, around 53% of the research focuses on RE automation in analysis and specifications, 40% focuses on elicitation, validation, and requirements management, and 7% focuses on requirements quality. NLP is the most used method in elicitation and specification, while for analysis, machine learning, NLP, and goal-oriented models are mostly used in automatic RE. Furthermore, many papers use specific models and methods for validation and requirements management. From the domain analysis results, it is obtained that more than half of the papers contribute directly to the RE domain, and some contribute to the development of RE automation in the software application domain. 
  

Green Requirement Engineering: Towards Sustainable Mobile Application Development and Internet of Things

Mobile usage statistics show the one thing that cannot be overlooked, which is the overwhelming usage of smartphones. According to the statistics, there are approximately 6.4 billion users of smartphones. Considering the world population, this rate of smart phone usage is more than 80%. Mobile development is the fastest prominent trend, although web development cannot be denied. However, the fact is that mobile platforms are considered cumbersome and complex when it comes to accomplishing requirement engineering processes, especially when mobile applications are combined with the Internet of Things (IoT). These complexities result in barriers to sustainable mobile development. The difficulty and differences occur due to various limitations, either that of mobile devices or others. Some of those from mobile devices include processor, battery, and touch screens, user experience in terms of touch screens, user context, and interactive behaviors. Other limitations include the difference in the software development lifecycle and the difference in the software development process due to inconsistency in user requirements with the aforementioned limited device capabilities. The target objective of this research is to investigate and identify all possible challenges related to mobile applications and connected mobile devices (IoT) while executing the requirement engineering process. This study can further the existing state of knowledge by contributing to the list of challenges faced in the requirement gathering process of mobile application development. Furthermore, it can also help practitioners, specifically those involved in the requirement gathering process, to carefully consider these challenges before executing the requirement engineering process.

Competencies of a Requirement Engineer -Systematic Literature Review Protocol

Requirement Engineering (RE) is a core activity of software engineering that guarantees successful project delivery within time and budget. It needs to be considered with respect to the competencies and skills of RE to effectively execute the RE processes and individual sustainability of requirement engineers. Several skill and competency frameworks are proposed and remember in various fields, however there is no competency framework for software requirement engineers. In this research work a systematic literature review protocol is presented as an initial step to design the framework that constitutes the competencies required for RE. Focusing on the competencies and skills of a requirement engineer will help to effectively perform requirement engineering tasks that will eventually lead to the success of a project.

On identifying possible artificial intelligence applications in requirements engineering processes

Managing an ever-growing number of requirements is a time consuming and highly complex activity in product development projects. With the rise of Artificial Intelligence (AI) in the last decades, algorithms are now capable of supporting Requirements Engineering (RE) tasks. The algorithm’s ability to intelligently process natural language data as well as the application in RE have been published extensively. In established RE processes however, it is often unclear, where AI algorithms can be utilized. The result is a significant imbalance between state-of-the-art AI algorithms and their application rates in real RE processes. One of the reasons is, that current models of RE processes aren’t able to convey the needed information for the identification of suitable tasks. Therefore, this paper aims to provide a framework of finite and standardized process steps with a data processing-oriented perspective, that can be used to systematically identify the points in the RE processes where AI algorithms can be applied. With the standardized process steps of this framework, established RE processes can be abstracted and expressed in a way that is compatible with the scope of AI algorithms. Due to the finite number of standardized process steps, libraries of suitable AI algorithms for the defined process steps can be built, so that their applicability can be efficiently assessed. The presented framework was developed collaboratively during a research project with industry participation.

Semi-structured expert interview-based requirements elicitation for a digitalized production ramp-up

Due to the ever-shortening innovation cycles and the rapid change of customer demands, enterprises introduce new, innovative, and modern products at an increasingly faster frequency and desirably lower costs. The technological change of products and mass customization increase the product complexity. This development requires manufacturing enterprises to perform more frequent production ramp-ups. Many production ramp-up projects miss the time, cost, and quality targets, causing manufacturing enterprises to lose potential profit due to later market introduction. Although digital tools are widely applied during the serial production phase, their potential during production ramp-up is hardly investigated in the scientific literature. Moreover, no guidelines exist on how to use digital tools during the production ramp-up in various industries. To provide data-driven support for the production ramp-up phase, requirements for the functionality of digital tools need to be defined. Henceforth, this paper applies a requirements engineering (RE) approach to elicit the requirements for digital tools to support the production ramp-up phase based on a comprehensive literature review and semi-structured expert interviews. In total, 13 experts from seven different industries participated in the interviews. After introducing the necessary theoretical foundations and the current state of research in ramp-up management literature, the RE process is described in detail. The RE process is based on user stories – an agile development tool – and the ISO 29148, which outlines an international standard for RE processes. The result is a set of requirements for the functionality of digital tools during the production ramp-up phase. Finally, the paper presents an outlook on future research perspectives for applying the elicited requirements in practice.

Empirical Analysis of Software Success Rate Forecasting During Requirement Engineering Processes

Forecasting on success or failure of software has become an interesting and, in fact, an essential task in the software development industry. In order to explore the latest data on successes and failures, this research focused on certain questions such as is early phase of the software development life cycle better than later phases in predicting software success and avoiding high rework? What human factors contribute to success or failure of a software? What software practices are used by the industry practitioners to achieve high quality of software in their day-to-day work? In order to conduct this empirical analysis a total of 104 practitioners were recruited to determine how human factors, misinterpretation, and miscommunication of requirements and decision-making processes play their roles in software success forecasting. We discussed a potential relationship between forecasting of software success or failure and the development processes. We noticed that experienced participants had more confidence in their practices and responded to the questionnaire in this empirical study, and they were more likely to rate software success forecasting linking to the development processes. Our analysis also shows that cognitive bias is the central human factor that negatively affects forecasting of software success rate. The results of this empirical study also validated that requirements’ misinterpretation and miscommunication were the main causes behind software systems’ failure. It has been seen that reliable, relevant, and trustworthy sources of information help in decision-making to predict software systems’ success in the software industry. This empirical study highlights a need for other software practitioners to avoid such bias while working on software projects. Future investigation can be performed to identify the other human factors that may impact software systems’ success.

Introducing Refined Agile Model (Ram) in the Context of Bangladesh's Software Development Environment Concentrating on the Improvement of Requirement Engineering Process

Introducing Refined Agile Model (Ram) in the Context of Bangladesh's Software Development Environment Concentrating on the Improvement of Requirement Engineering Process

MiniPI: Minimizing Power Imbalance among Stakeholders for Quality Software Product

The role of requirements elicitation is crucial in the software requirement engineering process as the requirement engineer has to extract the accurate requirements from different stakeholders. However, the problem emerges when the requirement team could not prioritize the extracted requirements because the requirement’s nature may vary as different categories of stakeholders have their own perspectives. This ultimately produces a power imbalance among stakeholders. Therefore, minimizing the power imbalance of software requirements among different categories of stakeholders is fundamentally important for a quality software product. Although many contributions have been made to this subject in the past, there is still a research gap available for minimizing the power imbalance among stakeholders. In this paper, we present a novel approach for minimizing the effects of power imbalance by age-sampling among different categories of stakeholders into three groups and then by age-mapping the requirements. After gathering questionnaires from stakeholders, the concerned parties determine the attributes of the Kano model through the filled Kano’s questionnaires and afterward, the satisfaction index is calculated by taking the values of the relevant age group into account, which eventually minimizes the power imbalance among stakeholders. In order to verify our methodology, we have performed quantitative analysis by calculating index values and applied verified Kano’s satisfaction formula to calculate the overall satisfaction index which improves the quality level of a software product.

GoEliTool for Software Requirements Elicitation using Goal-Oriented Approach

Requirements engineering (RE) is an essential initial stage in software engineering. The RE process begins with the elicitation stage. This stage collects all user requirements that must be fulfilled by the system which will be developed. A goal-oriented approach is an effective approach used to automate the RE process. The development of goal-oriented input document standards is one of the important issues that has not been widely studied. Therefore, this study developed a goal-oriented input document standard for the requirements elicitation process. A tool is developed based on the form of the input document that has been generated. The development of standard forms of input documents begins with literature study and data collection, analysis, design of standard forms of documents, tool design, tool development, and testing. At the analysis stage, a logical framework and element structure is formulated in a goal-oriented approach. Furthermore, the standard form of input documents is developed. The standard form of the document becomes a guideline for developing tools to process data requirements from elicitation results. Tool testing is carried out using black-box testing. The test results show that the tool can work according to the planned function. The trial of the use of the tools was carried out using five requirements datasets. The results of testing and using the tool through the requirements dataset show that GoEliTools can be used to record data on the requirements of several users for the development of an information system. 

An Efficient Identification of Security Threats in Requirement Engineering Methodology.

Today, we completely rely on Information Technology (IT) applications for every aspect of daily life, including business and online transactions. In addition to using these IT-enabled applications for business purposes, we also use WhatsApp, Facebook, and a variety of other IT applications to communicate with others. However, there will undoubtedly be a drawback to every benefit. Since everything is linked to the Internet, there are many opportunities for security to be compromised. To address this, we are working to identify security threats early on in the software development process, specifically during the requirements phase. During the requirement engineering process, an engineer can recognize the security specifications in a more structured manner to create threat-free software. In our research work, we suggest the Identification of Security Threats during Requirement Engineering (ISTDRE) technique for detecting security risks throughout the requirement engineering process. The four points that make up this ISTDRE technique are Hack Point (HP), Speculation Point (SP), Trust Point (TP), and Reliable Point (RP). The new ISTDRE methodology will be validated using a case study of an ERP system involving two currently used methodologies: Model Oriented Security Requirements Engineering (MOSRE) and System Quality Requirements Engineering (SQUARE).

Reducing Requirements Ambiguity via Gamification: Comparison with Traditional Techniques.

Requirements elicitation is one of the most significant activities of requirements engineering (RE) process. Poorly specified requirements can lead to a failed project. Various elicitation techniques are used to elicit requirements from the users and other stakeholders, each having its own pros and cons. Lack of user engagement, less user involvement, textual nature of the requirements, time taking process are some of the major problems that make it difficult to perform elicitation via traditional techniques. Moreover, these problems further create other challenges such as ambiguity, inconsistency, and incompleteness in requirements. Currently, researchers have focused on reducing ambiguity in requirements with the help of different techniques such as natural language processing techniques, requirement templates, and formal methods; however, these techniques work on reducing ambiguity during specification or from specified requirements. One of the “young' and exciting way of engaging users in requirements elicitation of a system is “Gamification', which helps in user engagement into the system. We intend to discover how gamification helps in reducing ambiguity by engaging stakeholders in an interactive manner. In this review study, we have reviewed traditional techniques used to detect and reduce requirements ambiguity. On the contrary, we have also presented the significance of gamification in requirements elicitation and the popular but effective game elements used in similar systems. Furthermore, this study highlights the significance of using gamification in requirements elicitation, which is beneficial to software development team as well as the users involved in the system.

Towards dealing with commonly occurring requirements engineering process issues during software development outsourcing.

Due to specific advantages, the volume of Software Development Outsourcing (SDO) is rapidly increasing. Because of challenges arising from the Requirements Engineering (RE) process, the anticipated benefits of SDO are not achieved in case of several projects. The objective of this research work is to recommend RE practices for addressing the commonly arising RE process issues in the case of SDO. For this reason, a thorough literature review has been undertaken, as well as two questionnaire surveys have been performed with skilled SDO industry practitioners. The surveys have been done by utilizing semi-supervised style and employing Convenience Sampling method. The 50 percent rule and a four-point Likert Scale have also been used to determine the advantages of RE practices for dealing with the issues. A comprehensive list of 147 RE practices has been extracted by conducting a Focus Group session. Furthermore, the 147 RE practices have been ranked by applying Numerical Assignment and Hundred Dollar Techniques during two Focus Group sessions. The detection and adaptation of RE practices aids in enhancing the SDO RE process, evading SDO failures, and achieving the associated SDO advantages.

A German Smartphone-Based Self-management Tool for Psoriasis: Community-Driven Development and Evaluation of Quality-of-Life Effects.

BackgroundPsoriasis is a chronic disease characterized by inflammation, increased scaling, itching, and other symptoms. Psoriasis is not contagious, but patients have often felt shunned. Therefore, in addition to psoriasis symptoms, stress, anxiety, and depression can also affect quality of life (QoL). Surveys show that only a quarter of patients are satisfied with the success of their therapy. However, in addition to medical therapy, self-management can also make it easier to deal with chronic diseases like psoriasis.ObjectiveThe aim of this project was to develop a smartphone-based self-management tool (SMT) specifically for patients with psoriasis using a community-driven process. The impact of the SMT on QoL as well as its acceptance and usability were evaluated.MethodsIn collaboration with an internet-based self-help community, 2 user surveys were conducted to determine the requirements for a smartphone-based SMT. The surveys consisted of semistructured questionnaires asking for desired features in an SMT for psoriasis. A pilot study was conducted to evaluate QoL, acceptance, and usability. Community users were recruited to use the app for 21 days and complete the Dermatology Life Quality Index (DLQI) questionnaire at the beginning (T0) and end (T1). Afterward, participants were asked to complete another questionnaire on usability and ease of use.ResultsSMT requirements were collected from 97 members of an internet-based community. The SMT was built as a progressive web app that communicates with a server back end and an Angular web app for content management. The app was used by 15 participants who also provided qualitative feedback, and 10 participants answered all questionnaires. The average DLQI score was 7.1 (SD 6.2) at T0 and 6.9 (SD 6.6) at T1. The minimal required sample size of 27 was not reached.ConclusionsThe high degree of community participation in the development process and the responses during the requirement engineering process indicated that there is a general need for an independently developed SMT for patients with psoriasis. However, the feedback received after app use shows that the SMT does not meet the needs of the community. It can be concluded that a more customizable app is needed. The focus and needs of the users were very heterogeneous. Similar developments and research could benefit from the findings of this project.

Understanding general concepts of requirements engineering through design thinking: An experimental study with students

AbstractTeaching requirements engineering (RE) is one of the challenging parts of any software engineering (SE) education curriculum because it deals with understanding the problem from multiple perspectives and acquiring a holistic view of the system. Academicians have adopted several innovative approaches to teaching RE concepts to students, and design thinking (DT) is one of them. DT integrates the needs of people, technology, and requirements and can help learn and apply human‐centered techniques to solve problems. An experimental study is conducted with 315 undergraduate students to realize how they can learn the RE process effectively by combining DT methods with the RE concepts for an effective RE education. This study intends to identify how this integration help students in using multiple elicitation methods, better visualization and understanding of the system requirements, and achieving various teaching objectives. An experimental study was planned and executed with students by integrating DT methods for RE activities from the beginning of problem definition to the final solution. The evaluation was done by collecting students' responses to pre‐survey and post‐survey questions capturing the students' perspectives on the RE and DT techniques. The students' responses suggested that the DT drive RE activities to improve their learning, thinking abilities, engagement with the team, and teamwork. Additionally, the students' artifacts during the DT process have also been evaluated. The use of DT methods helped in understanding the elicitation process and, consequently, helped reach the solution.